All Dart classes require a licenses.licx file in the executing assembly’s project, containing an entry for each licensed class. Without the licenses.licx, a runtime license will not be generated and compiled into the assembly, and a license exception will be thrown at runtime.
When a licensed control or component is added to a project using the Visual Studio designer, a licenses.licx file will be automatically generated if one does not already exist, and an entry for the class added.
When developing an assembly with no design surface such as a console application, or when instantiating a licensed class in code, the licenses.licx file must be added manually. If a licenses.licx file is not present in the project, add a new text file named "licenses.licx" to the project (not the solution) from the Solution Explorer. Add a single line to the licenses.licx that includes the fully-specified class name and the assembly name, separated by a comma. For example:
Dart.Emulation.Vt, Dart.Emulation
Web Site projects include an App_Licenses.dll that must be rebuilt when changes are made to the licenses.licx file or when migrating from trial to licensed operation. The App_Licenses.dll can be rebuilt by right-clicking on the licenses.licx file in the Solution Explorer and selecting the "Rebuild Runtime Licenses" option.
Because PowerShell does not execute compiled code and its scripts are generally modifiable by end users, a development or trial license is required on any machine executing scripts. If an environment other than PowerShell is being used or another distribution method is desired, please contact support@dart.com for additional options.
For compilation environments that do not recognize the licenses.licx file, a license resource may be generated with the .NET or MONO lc.exe utility on a licensed machine and added to the project as an embedded resource, or linked during compilation using the appropriate resource switch. For specific instructions, check with the environment's manufacturer.
Dart components include a 30-day introductory trial period. With the exception of trial messages and trial runtime license expiration exceptions, runtime trial operation is the same as licensed operation.
A 7-day runtime license will be embedded in assemblies compiled during the trial period. After 7 days, Dart classes will throw an exception and the assembly will no longer function. The 7-day runtime license can be reset within the 30-day trial period by recompiling the project.
A trial installation can be licensed by purchasing and activating a Product Key.
A Developer License is required to compile licensed assemblies. A valid Product Key is required to generate a Developer License. Each Developer License is machine and version specific; major and minor version increments (for example, 4.0, 4.1 and 5.0) require separate Product Keys and Developer Licenses, build and revision do not.
Product and license upgrades are available through the Customer Center to developers with an active subscription.
Run the included license activation utility from the Activate PowerTCP Emulation for .NET 4.7 shortcut in the product's Start Menu program group. The utility will guide you through the registration and activation process. Once complete, the Developer License file will be emailed to you. Copy the dartlic file attached to the email to the following location:
Program Files (x86) \ Dart \ PowerTCP Emulation for .NET \ 4.7 \ bin
This location is also accessible from the 'Binaries Folder' shortcut in the product's Start Menu program group.
Note: On UAC-enabled operating systems, the dartlic file may need to be saved to a non-UAC-protected location before copying it to the aforementioned location.
If Internet access is not available on the development machine, the activation utility provides a URL for activating the license on a machine with Internet access so that the Developer License can be retrieved and copied to the development machine.
Note: All licensing messages and exceptions are logged to the Application Event Log with "Dart Components" as the event source. If the "Dart Components" event source could not be created, messages are logged under the ".NET Components" event source. The Application Event Log can be examined for licensing messages and exceptions in situations where message boxes cannot be displayed or no GUI is present.
Dart components support xcopy deployment and do not require any files other than the component dll and compiled project assemblies.